I haven't still test the code in action, I'll attach a screenshot once I'm done and open the PR.

Hey @TharakaUJ,

Thanks a lot for the PR.

In the Next.js SDK, since we have a server side, token handling is done at the server level.
Have a look at https://github.com/asgardeo/javascript/blob/main/packages/nextjs/src/server/actions/getAccessToken.ts.
We can follow the same way.

I’ve made some updates to the last commit.

I adjusted the return types of a few interfaces to include undefined where necessary, to keep the types aligned and avoid inconsistencies.

For the server action APIs, I followed the same pattern used in getAccessToken.

Since the sessionPayload currently only contains accessToken and sessionId, retrieving the idToken and decodedIdToken directly from it wasn’t possible. Therefore, I used the client instance to obtain those values.

I’ve attached screenshots demonstrating how getAccessToken, getIdToken, and getDecodedIdToken are working.

I still need to verify the exchangeToken API behavior, I’ll update once that’s confirmed. In the meantime, please let me know if any changes are required.

Thank you!

⚠️ No Changeset found

If these changes should result in a version bump, you need to add a changeset.

Refer Release Documentation to learn how to add a changeset.